fix: metrics.json could use more data - #722

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: bdeaaf86-66b3-42c5-875c-26191f443d73
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 6.929s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

Hi @Mr-Neutr0n thanks for the contribution! I didn't look deeply into it yet, but doesn't it overlap with metrics_by_type?

Thanks for checking. metrics_by_type remains the per-requirement link coverage map, while needs_overview adds total, local versus external, and per-type counts across all needs, including non-requirement types, so the two sections serve different purposes. The current ECA failure is a legal-agreement gate rather than a code or test failure, so it needs to be resolved through the Eclipse contributor process.

I think here, we have to figure out what more data means firstly before we can go to the implementation phase.

That is our bad @Mr-Neutr0n , we will clarify this and come back once we have an answer.

Hi @MaximilianSoerenPollak - no rush at all; just checking whether the "more data" definition landed on your side. Happy to pick this back up whenever you have an answer, and fine to close if it is no longer a priority.